- 
                Notifications
    You must be signed in to change notification settings 
- Fork 13.4k
fix(select): add missing filled type styles #30755
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| The latest updates on your projects. Learn more about Vercel for GitHub. 
 | 
        
          
                ...ustom/select.e2e.ts-snapshots/select-custom-diff-ionic-md-ltr-light-Mobile-Firefox-linux.png
          
            Show resolved
            Hide resolved
        
      There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joselrio Looking at Figma, these seemed the expected tokens to use
Co-authored-by: Bernardo Cardoso <[email protected]>
Co-authored-by: Bernardo Cardoso <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The solid background looks good, but I think you need to change the select-text when it has a value (has-value class).
Issue number: resolves # --------- This is based on #30755 PR to try to clean up things. <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? - Select text color was not according design - Fill solid type was missing the background color ## What is the new behavior? - Added the expected color to the select text - Added missing background color variable to the fill solid type ## Does this introduce a breaking change? - [ ] Yes - [X] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/docs/CONTRIBUTING.md#footer for more information. --> --------- Co-authored-by: ionitron <[email protected]>
Issue number: resolves #
What is the current behavior?
What is the new behavior?
Does this introduce a breaking change?